[SET] SETBoundary#9107
Closed
bartlomiejbloniarz wants to merge 10 commits into
Closed
Conversation
This PR introduces a new concept for SETs, called SharedTransitionBoundary. It is supposed to replace the current approach where we use Screens from RNScreens to separate which shared elements should be displayed. With the new approach one can still wrap a screen to get the old behavior, but also new patterns are available, such as running a SharedTransition within one RNScreen. Main pros of this solution: - easier to adapt to different navigators (this allows us to use the TabNavigator with no weird native changes) - more customization options for users - no native dependency on RNScreens Cons: - the minimal manual setup that has to be done to enroll a RNScreen in running transitions - we have to guess the target boundary when doing a native back gesture on iOS. This should not be a big problem for the usual use-case Screenless example ghstack-source-id: 0464881 Pull Request resolved: #9036
bartlomiejbloniarz
force-pushed
the
@bartlomiejbloniarz/set-boundary-2
branch
from
155d84c to
d46a639
Compare
pull Bot
pushed a commit
to esinanturan/react-native-reanimated
that referenced
this pull request
Jun 15, 2026
## Summary This MR introduces `<SharedTransitionBoundary>`. It cherrypicks commits from software-mansion#9107 and software-mansion#9132 and resolves conflicts. Those MR are combined into one to keep main branch consistent. NOTE: Found a non-deterministic bug on Android (check recording at 1:41). Not sure if this is a regression. ## Test plan 1. Check the new `[SET] Screenless Basic` example 2. Check `[SET] *` examples for regressions in FabricExample app on iOS and on Android ## Attachments ### iOS after https://github.com/user-attachments/assets/fa74bd0b-66b6-48c0-97d7-b17fb7b2f357 ### Android after https://github.com/user-attachments/assets/eef60cfe-53ff-46a5-ae4c-2557b275ae2e --------- Co-authored-by: Bartłomiej Błoniarz <bartlomiej.bloniarz@swmansion.com> Co-authored-by: Satyajit Sahoo <satyajit.happy@gmail.com> Co-authored-by: Bartłomiej Błoniarz <bartlomiej.bloniarz@gmail.com> Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:
This PR introduces a new concept for SETs, called SharedTransitionBoundary. It is supposed to replace the current approach where we use Screens from RNScreens to separate which shared elements should be displayed. With the new approach one can still wrap a screen to get the old behavior, but also new patterns are available, such as running a SharedTransition within one RNScreen.
Main pros of this solution:
Cons:
Test Plan:
Screenless example